<!DOCTYPE html>
<html class="client-nojs vector-feature-night-mode-disabled vector-feature-language-in-header-enabled vector-feature-language-in-main-page-header-disabled vector-feature-page-tools-pinned-disabled vector-feature-toc-pinned-clientpref-1 vector-feature-main-menu-pinned-disabled vector-feature-limited-width-clientpref-1 vector-feature-limited-width-content-enabled vector-feature-custom-font-size-clientpref-1 vector-feature-appearance-pinned-clientpref-1 vector-sticky-header-enabled" lang="en" dir="ltr"><head>
<meta charset="UTF-8">
<title>Problem-oriented development</title>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<link rel="canonical" href="https://en.wikipedia.org/wiki/Problem-oriented_development"> <link href="./mw/ext.cite.styles.css" rel="stylesheet" type="text/css">
<link href="./mw/skins.vector.icons.css" rel="stylesheet" type="text/css">
<link href="./mw/skins.vector.search.codex.styles.css" rel="stylesheet" type="text/css">
<link href="./mw/skins.vector.styles.css" rel="stylesheet" type="text/css">
<link href="./mw/user.styles.css" rel="stylesheet" type="text/css">
<meta name="ResourceLoaderDynamicStyles" content="">
<link rel="stylesheet" type="text/css" href="./mw/site.styles.css">
<link rel="stylesheet" type="text/css" href="./mw/noscript.css">
<link rel="stylesheet" type="text/css" href="./footer.css">
<link rel="stylesheet" type="text/css" href="./vector-2022.css">
</head>
<body class="skin--responsive skin-vector skin-vector-search-vue mediawiki ltr sitedir-ltr mw-hide-empty-elt ns-0 ns-subject page-Problem-oriented_development rootpage-Problem-oriented_development skin-vector-2022 action-view">
<div class="mw-page-container">
<div class="mw-page-container-inner">
<div class="mw-content-container">
<main id="content" class="mw-body">
<header class="mw-body-header vector-page-titlebar">
<h1 id="firstHeading" class="firstHeading mw-first-heading">
<span id="openzim-page-title" class="mw-page-title-main"><span class="mw-page-title-main">Problem-oriented development</span></span>
</h1>
</header>
<a id="top"></a>
<div id="bodyContent" class="vector-body ve-init-mw-desktopArticleTarget-targetContainer" aria-labelledby="firstHeading" data-mw-ve-target-container="">
<div id="mw-content-text" class="mw-body-content mw-content-ltr" lang="en" dir="ltr"><div class="mw-content-ltr mw-parser-output" lang="en" dir="ltr"><p><b>Problem-Oriented Development</b> is an emerging paradigm of computing that emphasises problems (as opposed to requirements) as the primary subject of scrutiny by software engineers. As such, Problem-Oriented Development is concerned with:
</p>
<ul><li>Investigating the structure of organisational problems as addressed by Software Engineering;</li>
<li>Providing formalisms for modelling and representing problems;</li>
<li>Providing guidance and frameworks for problem analysis and decomposition;</li>
<li>Defining techniques for formally justifying solutions (e.g. by associating problem components with solution components);</li>
<li>Supporting knowledge reuse during problem analysis (e.g. through problem patterns).</li></ul>
<meta property="mw:PageProp/toc">
<div class="mw-heading mw-heading2"><h2 id="Specific_Approaches">Specific Approaches</h2></div>
<ul><li>Problem-Oriented Software Engineering provides a formal definition of problems, and a framework for associating problems with solutions through formal, logical arguments;<sup id="cite_ref-1" class="reference"><a href="#cite_note-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup></li>
<li><a href="Problem_Frames" class="mw-redirect" title="Problem Frames">Problem Frames</a> provide a framework for defining empirical models of software engineering problems which are grounded in the physical world. The Problem Frames approach also provides a set of elementary problem patterns;</li>
<li>The Domain Theory <sup id="cite_ref-2" class="reference"><a href="#cite_note-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup> hypothesises a set of cognitive "deep structures" corresponding to components of <a href="Domain_knowledge" title="Domain knowledge">domain knowledge</a> and draws on these to provide a framework for modelling software problems.</li></ul>
<div class="mw-heading mw-heading2"><h2 id="Research_Influences_of_Problem-Oriented_Development">Research Influences of Problem-Oriented Development</h2></div>
<p>Knowledge Engineering is a field of computer science which offers a significant body of work on problem-solving methods. Problem-solving methods are patterns of reasoning that are applied to solve specific problems.<sup id="cite_ref-3" class="reference"><a href="#cite_note-3"><span class="cite-bracket">[</span>3<span class="cite-bracket">]</span></a></sup> The work on problem abstractions within knowledge engineering can therefore provide a basis for research in software engineering.
</p><p><a href="Cognitive_Science" class="mw-redirect" title="Cognitive Science">Cognitive Science</a>, which may be defined as the study of the nature of intelligence, offers a basis for studying the cognitive structures that domain experts develop of problems, as well as for better understanding human approaches to problem solving. The Domain Theory is one example of the influence of cognitive science in Problem-Oriented Development research.
</p>
<div class="mw-heading mw-heading2"><h2 id="Events">Events</h2></div>
<ul><li>The First International Workshop on Problem-Oriented Development (POD-2009) will be hosted by the TOOLS-EUROPE 2009 conference.</li></ul>
<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>
<div class="mw-references-wrap"><ol class="references">
<li id="cite_note-1"><span class="mw-cite-backlink"><b><a href="#cite_ref-1">^</a></b></span> <span class="reference-text">J. Hall, L. Rapanotti, M. Jackson, "Problem Oriented Software Engineering: Solving the Package Router Control Problem", <i>IEEE Transactions on Software Engineering, Vol. 34, Issue 2.</i></span>
</li>
<li id="cite_note-2"><span class="mw-cite-backlink"><b><a href="#cite_ref-2">^</a></b></span> <span class="reference-text">A. Sutcliffe, <i>The Domain Theory: Patterns for Knowledge and Software Reuse</i>, CRC Press, March 2002</span>
</li>
<li id="cite_note-3"><span class="mw-cite-backlink"><b><a href="#cite_ref-3">^</a></b></span> <span class="reference-text">D. Fensel, E. Motta, "Structured development of problem solving methods", <i>IEEE Transactions on Knowledge and Data Engineering, Vol. 13, Issue 6</i></span>
</li>
</ol></div></div><!--htdig_noindex--><div><div class="zim-footer">
This article is issued from <a class="external text" title="Last edited on 2021-10-13" href="https://en.wikipedia.org/wiki/?title=Problem-oriented_development&oldid=1049807711">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.
</div>
</div><!--/htdig_noindex--></div>
</div>
</main>
</div>
</div>
</div>
</body></html>